Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Set resource limit for kube-ui addon container. #10778

Merged
merged 1 commit into from Jul 6, 2015

Conversation

dchen1107
Copy link
Member

This is what I left from #10653 for newly introduced addon container: kube-ui. Measurement is based on current default configuration for GCE / GKE (?) and AWS: 4 nodes, 30~50 pods per node.

Based on measurement, kube-ui uses tiny bit of resources on both cpu and memory. I decided to allocate 100m for cpu even they all use less than that since it matches today's default setting from LimitRange of default namespace anyway. For memory it uses ~10M after many poke and explore on ui. I allocated 50M to it.

cc/ @zmerlynn @lavalamp @bgrant0607

@dchen1107
Copy link
Member Author

#10335

cc/ @eparis and @justinsb for valgrant case.

@lavalamp
Copy link
Member

lavalamp commented Jul 6, 2015

LGTM

1 similar comment
@zmerlynn
Copy link
Member

zmerlynn commented Jul 6, 2015

LGTM

@zmerlynn zmerlynn added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jul 6, 2015
@eparis
Copy link
Contributor

eparis commented Jul 6, 2015

LGTM I sure hope we have 50M to spare.

@k8s-bot
Copy link

k8s-bot commented Jul 6, 2015

GCE e2e build/test failed for commit 747f84d.

@dchen1107
Copy link
Member Author

ok to test

@k8s-bot
Copy link

k8s-bot commented Jul 6, 2015

GCE e2e build/test passed for commit 747f84d.

yujuhong added a commit that referenced this pull request Jul 6, 2015
Set resource limit for kube-ui addon container.
@yujuhong yujuhong merged commit 8b63232 into kubernetes:master Jul 6, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lgtm "Looks good to me", indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

8 participants